Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45152ca7db049abd162c6edb80b2f062de850ba630cfc4670579eb8a73982b20

Tx prefix hash: bf23d528530404272c0922ba1db8de889fd5e562bb464cc600b00c502977e9d0
Tx public key: c7c45fbfc1af9987da573d3f76f5e6852d3c9ba39be6b54e6c3a1853d56fc71b
Timestamp: 1635072677 Timestamp [UCT]: 2021-10-24 10:51:17 Age [y:d:h:m:s]: 03:074:21:33:48
Block: 359459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 831880 RingCT/type: yes/0
Extra: 01c7c45fbfc1af9987da573d3f76f5e6852d3c9ba39be6b54e6c3a1853d56fc71b02110000000e5410958b000000000000000000

1 output(s) for total of 39.533341516000 dcy

stealth address amount amount idx
00: ba89fd592c91358363be36184ffb3c1cc0a159b37fc1117a0cc4f47654cdd047 39.533341516000 731980 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": 359469, "vin": [ { "gen": { "height": 359459 } } ], "vout": [ { "amount": 39533341516, "target": { "key": "ba89fd592c91358363be36184ffb3c1cc0a159b37fc1117a0cc4f47654cdd047" } } ], "extra": [ 1, 199, 196, 95, 191, 193, 175, 153, 135, 218, 87, 61, 63, 118, 245, 230, 133, 45, 60, 155, 163, 155, 230, 181, 78, 108, 58, 24, 83, 213, 111, 199, 27, 2, 17, 0, 0, 0, 14, 84, 16, 149, 139, 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