Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3c56d06b11006cb880e1d646edfcb70b8d1ac3467c2de93794fc818ce24faeb

Tx prefix hash: a17ffcd34a8fe5b6dfb0b4bea690f6528b66c4e179195ec4e948a4397172d5e6
Tx public key: 605bd4f054e6976ee428871c1d95059629fd41e862ab9899cb9afb1fb899be38
Timestamp: 1717652952 Timestamp [UCT]: 2024-06-06 05:49:12 Age [y:d:h:m:s]: 00:360:12:59:49
Block: 1038101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257704 RingCT/type: yes/0
Extra: 01605bd4f054e6976ee428871c1d95059629fd41e862ab9899cb9afb1fb899be380211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70ef915fbde6411d4b877f84bd57477cd4c171de6d81721ee8be080fdecc94f 0.600000000000 1506660 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": 1038111, "vin": [ { "gen": { "height": 1038101 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70ef915fbde6411d4b877f84bd57477cd4c171de6d81721ee8be080fdecc94f" } } ], "extra": [ 1, 96, 91, 212, 240, 84, 230, 151, 110, 228, 40, 135, 28, 29, 149, 5, 150, 41, 253, 65, 232, 98, 171, 152, 153, 203, 154, 251, 31, 184, 153, 190, 56, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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