Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38fc6fffabc43700da3b84550711a0e9eaf91ded943950070762147ef23b5a19

Tx prefix hash: 536b7435fbce040c20b85a4f85813ae19aba31b3b6c35248c4a5fcb3713bf740
Tx public key: 2f229909c48ade2f8d3cbb9fe57f2eac4bfd7cf4d28dfb513b001f9aa420aa22
Timestamp: 1574651710 Timestamp [UCT]: 2019-11-25 03:15:10 Age [y:d:h:m:s]: 05:007:09:15:15
Block: 16854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148134 RingCT/type: yes/0
Extra: 012f229909c48ade2f8d3cbb9fe57f2eac4bfd7cf4d28dfb513b001f9aa420aa22021100000001f95225a5000000000000000000

1 output(s) for total of 539.705175824000 dcy

stealth address amount amount idx
00: 414d10fc1ce43a0af05c6fc0456ec64ebe68ce8734ef640b83cef7cf77336db2 539.705175824000 23938 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": 16864, "vin": [ { "gen": { "height": 16854 } } ], "vout": [ { "amount": 539705175824, "target": { "key": "414d10fc1ce43a0af05c6fc0456ec64ebe68ce8734ef640b83cef7cf77336db2" } } ], "extra": [ 1, 47, 34, 153, 9, 196, 138, 222, 47, 141, 60, 187, 159, 229, 127, 46, 172, 75, 253, 124, 244, 210, 141, 251, 81, 59, 0, 31, 154, 164, 32, 170, 34, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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