Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d1d7978b691a74c7d4bb72abc76e42e965ebca91509764f562713a4374197a

Tx prefix hash: 736eb5e9272adb3f4abe94a91ba64aa3531e3008f12422c96883260908010e0e
Tx public key: 4a1f2abf53f45fb82d9b3b71a60271400996d68cc27c5f244853d58f0547fe5c
Timestamp: 1703035248 Timestamp [UCT]: 2023-12-20 01:20:48 Age [y:d:h:m:s]: 01:210:03:40:07
Block: 916911 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410275 RingCT/type: yes/0
Extra: 014a1f2abf53f45fb82d9b3b71a60271400996d68cc27c5f244853d58f0547fe5c02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd00cf857a3ec7424f23378fd99b416025e895ae1fb5d958dccca8a76ef7746e 0.600000000000 1374473 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": 916921, "vin": [ { "gen": { "height": 916911 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd00cf857a3ec7424f23378fd99b416025e895ae1fb5d958dccca8a76ef7746e" } } ], "extra": [ 1, 74, 31, 42, 191, 83, 244, 95, 184, 45, 155, 59, 113, 166, 2, 113, 64, 9, 150, 214, 140, 194, 124, 95, 36, 72, 83, 213, 143, 5, 71, 254, 92, 2, 17, 0, 0, 0, 2, 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