Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 762cef7c44b82c79f6296473d8dd3fdde692ab7e8767e3c83c9f5792dde475bc

Tx prefix hash: 0d2e31c76ea693a1f496e9f7d1fade10e9d5437f6fee2e53a0c4907a1447c172
Tx public key: 13ad8de939d66362de60f559e2fb5d21a1f665fbd395c29b1e9e4e8a8a525e6f
Timestamp: 1736449105 Timestamp [UCT]: 2025-01-09 18:58:25 Age [y:d:h:m:s]: 00:163:02:37:35
Block: 1193782 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116242 RingCT/type: yes/0
Extra: 0113ad8de939d66362de60f559e2fb5d21a1f665fbd395c29b1e9e4e8a8a525e6f021100000011007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80c72223c3b0fec17476327fc41232a220bbead13d45eda4d2fb7210ad2308c1 0.600000000000 1680347 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": 1193792, "vin": [ { "gen": { "height": 1193782 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80c72223c3b0fec17476327fc41232a220bbead13d45eda4d2fb7210ad2308c1" } } ], "extra": [ 1, 19, 173, 141, 233, 57, 214, 99, 98, 222, 96, 245, 89, 226, 251, 93, 33, 161, 246, 101, 251, 211, 149, 194, 155, 30, 158, 78, 138, 138, 82, 94, 111, 2, 17, 0, 0, 0, 17, 0, 127, 151, 138, 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