Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e235cfc802b5d891bdc79a969f9b4b300e843574434daff0e1415c3c01878a3d

Tx prefix hash: 5bd0f5463fd1ece7f0c91fb6a573acffb1cb89de3c632a1054b0c79fcc109036
Tx public key: 2e3d95dc19f19439a586cfbd40d09a6d6c5e29dce323ffc561e37eac14eb8632
Timestamp: 1708708358 Timestamp [UCT]: 2024-02-23 17:12:38 Age [y:d:h:m:s]: 01:261:08:02:15
Block: 963940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445517 RingCT/type: yes/0
Extra: 012e3d95dc19f19439a586cfbd40d09a6d6c5e29dce323ffc561e37eac14eb863202110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21625cebe0bc7ff6954a007ee1a7ee5029d653c8dd109b76622c5eac3e4cead0 0.600000000000 1423667 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": 963950, "vin": [ { "gen": { "height": 963940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21625cebe0bc7ff6954a007ee1a7ee5029d653c8dd109b76622c5eac3e4cead0" } } ], "extra": [ 1, 46, 61, 149, 220, 25, 241, 148, 57, 165, 134, 207, 189, 64, 208, 154, 109, 108, 94, 41, 220, 227, 35, 255, 197, 97, 227, 126, 172, 20, 235, 134, 50, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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