Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc90d550966e4abd8f3196772e58634efbd981528f15f30f2c53ed470121e7a7

Tx prefix hash: cde98dcd341f5cd0f654822bd966652e92c6271b67ef5f17a648eabc571065ac
Tx public key: 3a20e0d406d275d0de96f1aa74d5d969a1d34ba598f7ed1ee27ee3586f463292
Timestamp: 1674734295 Timestamp [UCT]: 2023-01-26 11:58:15 Age [y:d:h:m:s]: 02:286:08:55:58
Block: 683159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724025 RingCT/type: yes/0
Extra: 013a20e0d406d275d0de96f1aa74d5d969a1d34ba598f7ed1ee27ee3586f463292021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.345111345000 dcy

stealth address amount amount idx
00: d4d34dcb10a992397d4c547fced0f8cc949277ad0d5321e8a128476e5af90968 3.345111345000 1125330 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": 683169, "vin": [ { "gen": { "height": 683159 } } ], "vout": [ { "amount": 3345111345, "target": { "key": "d4d34dcb10a992397d4c547fced0f8cc949277ad0d5321e8a128476e5af90968" } } ], "extra": [ 1, 58, 32, 224, 212, 6, 210, 117, 208, 222, 150, 241, 170, 116, 213, 217, 105, 161, 211, 75, 165, 152, 247, 237, 30, 226, 126, 227, 88, 111, 70, 50, 146, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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