Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5756392d2a5a9eef6e94945f84346e4ad44bee4be4dc7b80e09e75c4fa788dbb

Tx prefix hash: 6b3b27def472d2b7fe35466e06170681201f5158b257f79733c56b49b3f7f948
Tx public key: dd2786df2ff7319544d615a30bb402395bc09514bccfa5a5d00a6664262ff79e
Timestamp: 1732310172 Timestamp [UCT]: 2024-11-22 21:16:12 Age [y:d:h:m:s]: 00:001:06:24:12
Block: 1159509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 915 RingCT/type: yes/0
Extra: 01dd2786df2ff7319544d615a30bb402395bc09514bccfa5a5d00a6664262ff79e021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a627b70b5067e8c8327d43e186d60c75c76b4e22b1b3204b019841b2d7311316 0.600000000000 1645146 of 15

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": 1159519, "vin": [ { "gen": { "height": 1159509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a627b70b5067e8c8327d43e186d60c75c76b4e22b1b3204b019841b2d7311316" } } ], "extra": [ 1, 221, 39, 134, 223, 47, 247, 49, 149, 68, 214, 21, 163, 11, 180, 2, 57, 91, 192, 149, 20, 188, 207, 165, 165, 208, 10, 102, 100, 38, 47, 247, 158, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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