Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1af44df0f40ff8d084ce90c1996f57d677cbe606f04f3a8760b1f9cd56df0e5

Tx prefix hash: 7fd78adfe4d1ff8651517d557d1dbcca5a2f60420995828ce89c0416ecfff116
Tx public key: f10f0e521b56df0efb95d22ffe7005b790f26bfba08d0c5637e0b6394c5be624
Timestamp: 1701927423 Timestamp [UCT]: 2023-12-07 05:37:03 Age [y:d:h:m:s]: 01:193:00:06:07
Block: 907722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399027 RingCT/type: yes/0
Extra: 01f10f0e521b56df0efb95d22ffe7005b790f26bfba08d0c5637e0b6394c5be62402110000000375e3f0e9000000000000000000

1 output(s) for total of 0.603031742000 dcy

stealth address amount amount idx
00: 2b7759e87cc9e0296579ee96ae154eb14a63eda1db8695e56cf4867a363665f2 0.603031742000 1364715 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": 907732, "vin": [ { "gen": { "height": 907722 } } ], "vout": [ { "amount": 603031742, "target": { "key": "2b7759e87cc9e0296579ee96ae154eb14a63eda1db8695e56cf4867a363665f2" } } ], "extra": [ 1, 241, 15, 14, 82, 27, 86, 223, 14, 251, 149, 210, 47, 254, 112, 5, 183, 144, 242, 107, 251, 160, 141, 12, 86, 55, 224, 182, 57, 76, 91, 230, 36, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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