Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5cae78d2d77de188adbcfe613ec128f2f14bd072263952de525a440b0c1c39

Tx prefix hash: 329023063e39757346931e356d9a4bae42b74cf8f54a4f50b12571f797f07ea6
Tx public key: 9c80632a063811d0223c5a7156576dfa3ca5ee0fa44b0227716ec7cd8831f4c1
Timestamp: 1696221009 Timestamp [UCT]: 2023-10-02 04:30:09 Age [y:d:h:m:s]: 02:039:15:10:44
Block: 860619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 547964 RingCT/type: yes/0
Extra: 019c80632a063811d0223c5a7156576dfa3ca5ee0fa44b0227716ec7cd8831f4c102110000000175e3f0e9000000000000000000

1 output(s) for total of 0.863797682000 dcy

stealth address amount amount idx
00: 477662878c0c25f130be68b4d0e63b3fef56f897047a5f55c11dce64d286f122 0.863797682000 1314909 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": 860629, "vin": [ { "gen": { "height": 860619 } } ], "vout": [ { "amount": 863797682, "target": { "key": "477662878c0c25f130be68b4d0e63b3fef56f897047a5f55c11dce64d286f122" } } ], "extra": [ 1, 156, 128, 99, 42, 6, 56, 17, 208, 34, 60, 90, 113, 86, 87, 109, 250, 60, 165, 238, 15, 164, 75, 2, 39, 113, 110, 199, 205, 136, 49, 244, 193, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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