Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b845849de2e4ae0f19c9c728555a8803d0f5e50365285be2201c7f9ec9f119bc

Tx prefix hash: e2a47d3859f50ace6d26078438f8c7bc7d6e4876feaaf54a08a17d9c6bd5cd10
Tx public key: 2adcfead3d72a794fb2603d134c48558091cda68ef6c62fece2ae5fe5be20b00
Timestamp: 1718421696 Timestamp [UCT]: 2024-06-15 03:21:36 Age [y:d:h:m:s]: 00:332:15:33:22
Block: 1044475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237745 RingCT/type: yes/0
Extra: 012adcfead3d72a794fb2603d134c48558091cda68ef6c62fece2ae5fe5be20b00021100000001d9a56ff1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c300947782c3934922d1724bd38b44c40df298d70b83b9b40e8a17bda7d018f2 0.600000000000 1513794 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": 1044485, "vin": [ { "gen": { "height": 1044475 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c300947782c3934922d1724bd38b44c40df298d70b83b9b40e8a17bda7d018f2" } } ], "extra": [ 1, 42, 220, 254, 173, 61, 114, 167, 148, 251, 38, 3, 209, 52, 196, 133, 88, 9, 28, 218, 104, 239, 108, 98, 254, 206, 42, 229, 254, 91, 226, 11, 0, 2, 17, 0, 0, 0, 1, 217, 165, 111, 241, 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