Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d849b4db3cc4c334caeec0ae7a004b5481d55b80f3e8502971eb9fbcb3e6592d

Tx prefix hash: abb8ec0562692e1c61d0f48099292d7f4eb02996887cfce7924c03bfd86e581d
Tx public key: 4313901691263f881c404bda67b0841a678ce94b8d8333f3304ad359402051e5
Timestamp: 1577661414 Timestamp [UCT]: 2019-12-29 23:16:54 Age [y:d:h:m:s]: 05:115:11:27:07
Block: 34602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1232346 RingCT/type: yes/0
Extra: 014313901691263f881c404bda67b0841a678ce94b8d8333f3304ad359402051e50211000000024ac5aa02000000000000000000

1 output(s) for total of 471.357113428000 dcy

stealth address amount amount idx
00: a4b7d280162c93cd90a7c468fd273320b8105963c6a0f65d075b851862ad6da1 471.357113428000 58272 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": 34612, "vin": [ { "gen": { "height": 34602 } } ], "vout": [ { "amount": 471357113428, "target": { "key": "a4b7d280162c93cd90a7c468fd273320b8105963c6a0f65d075b851862ad6da1" } } ], "extra": [ 1, 67, 19, 144, 22, 145, 38, 63, 136, 28, 64, 75, 218, 103, 176, 132, 26, 103, 140, 233, 75, 141, 131, 51, 243, 48, 74, 211, 89, 64, 32, 81, 229, 2, 17, 0, 0, 0, 2, 74, 197, 170, 2, 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