Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384a034106610ceab9cebfb423d6374f561c54c71e65f0c58ea97e981fc77065

Tx prefix hash: 5cbd44ce0cacb86e0f89a3a94d737dfc500eef81da6cf4052a056e1c792c3616
Tx public key: beb47f7fc1636362efd2ee9525fa34eae205a6401afbfb9f5dc7bc9d83252390
Timestamp: 1733548422 Timestamp [UCT]: 2024-12-07 05:13:42 Age [y:d:h:m:s]: 00:109:03:54:15
Block: 1169772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77808 RingCT/type: yes/0
Extra: 01beb47f7fc1636362efd2ee9525fa34eae205a6401afbfb9f5dc7bc9d83252390021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09b03ea9ef563b0786c820d7c2ccf6542d4c2a904d29033d7ee39938cb8c0aff 0.600000000000 1655497 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": 1169782, "vin": [ { "gen": { "height": 1169772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09b03ea9ef563b0786c820d7c2ccf6542d4c2a904d29033d7ee39938cb8c0aff" } } ], "extra": [ 1, 190, 180, 127, 127, 193, 99, 99, 98, 239, 210, 238, 149, 37, 250, 52, 234, 226, 5, 166, 64, 26, 251, 251, 159, 93, 199, 188, 157, 131, 37, 35, 144, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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