Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f72f2de120152431d6fd59fd4fa89e62921e6112054918508fd8191c76361e3d

Tx prefix hash: d36a8ce51a7c84af9f1ed7276bc9aa57ddc6e3f4f39fa3356c99c329ca283db8
Tx public key: 63994f9bdd01aadeee43e169f8af7b49431414f272a9e253b36b19394922060c
Timestamp: 1701574900 Timestamp [UCT]: 2023-12-03 03:41:40 Age [y:d:h:m:s]: 01:048:18:12:09
Block: 904797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296191 RingCT/type: yes/0
Extra: 0163994f9bdd01aadeee43e169f8af7b49431414f272a9e253b36b19394922060c021100000001e08532b6000000000000000000

1 output(s) for total of 0.616640317000 dcy

stealth address amount amount idx
00: f60a8e76df0e9060cd5585c4cb41011d23491dc6a4558ec776416196659fdff3 0.616640317000 1361572 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 904807, "vin": [ { "gen": { "height": 904797 } } ], "vout": [ { "amount": 616640317, "target": { "key": "f60a8e76df0e9060cd5585c4cb41011d23491dc6a4558ec776416196659fdff3" } } ], "extra": [ 1, 99, 153, 79, 155, 221, 1, 170, 222, 238, 67, 225, 105, 248, 175, 123, 73, 67, 20, 20, 242, 114, 169, 226, 83, 179, 107, 25, 57, 73, 34, 6, 12, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8