Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02152cdc4bc98acbb3c831551b2f1ce131705870295610f6582f7b817644899f

Tx prefix hash: 6d04b755b9bbc54bd3374f25b26946dd83728148432ad8674f983cf13e4cc2b1
Tx public key: 64937eee8a93ac6bf66ec67c8a36d1a75c51c67f703ece92b0c4c544b5062514
Timestamp: 1574577411 Timestamp [UCT]: 2019-11-24 06:36:51 Age [y:d:h:m:s]: 05:102:01:32:26
Block: 16250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1215574 RingCT/type: yes/0
Extra: 0164937eee8a93ac6bf66ec67c8a36d1a75c51c67f703ece92b0c4c544b5062514021100000018fc8b7a00000000000000000000

1 output(s) for total of 542.197969236000 dcy

stealth address amount amount idx
00: bdb49cbd8d48665ccda3dfe644860c0a8af95f55d56aa8d2dc606a45139f18d7 542.197969236000 22554 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": 16260, "vin": [ { "gen": { "height": 16250 } } ], "vout": [ { "amount": 542197969236, "target": { "key": "bdb49cbd8d48665ccda3dfe644860c0a8af95f55d56aa8d2dc606a45139f18d7" } } ], "extra": [ 1, 100, 147, 126, 238, 138, 147, 172, 107, 246, 110, 198, 124, 138, 54, 209, 167, 92, 81, 198, 127, 112, 62, 206, 146, 176, 196, 197, 68, 181, 6, 37, 20, 2, 17, 0, 0, 0, 24, 252, 139, 122, 0, 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