Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b2418fc96c7123cf557bbce7a47683dc308b96191ea1af1ceda56a728c1c450

Tx prefix hash: e4b1c359278e176aff0d7f50234e760eb198d7a783fecc203f3552fd5af8021f
Tx public key: bf3ad353fbc1e56a9c2dc1b7e9ce683bd9b7f464981c8ee8da8bf1ad59967f59
Timestamp: 1712144871 Timestamp [UCT]: 2024-04-03 11:47:51 Age [y:d:h:m:s]: 01:048:01:44:43
Block: 992400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295382 RingCT/type: yes/0
Extra: 01bf3ad353fbc1e56a9c2dc1b7e9ce683bd9b7f464981c8ee8da8bf1ad59967f5902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0d5664be61175be30b7a77714fdb118e523ffb37e08341b3ab97e8e2e966428 0.600000000000 1452742 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": 992410, "vin": [ { "gen": { "height": 992400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0d5664be61175be30b7a77714fdb118e523ffb37e08341b3ab97e8e2e966428" } } ], "extra": [ 1, 191, 58, 211, 83, 251, 193, 229, 106, 156, 45, 193, 183, 233, 206, 104, 59, 217, 183, 244, 100, 152, 28, 142, 232, 218, 139, 241, 173, 89, 150, 127, 89, 2, 17, 0, 0, 0, 4, 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