Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 447c1015ad0b2f54a874457ffd3fec174e87233857dc1e25d955a094b9fe826e

Tx prefix hash: 35a8795249cdf72dfe97695c4574324665d875a7f4cb89cc89a4fad367c51625
Tx public key: 18245e6f46ed7c69b273613461206d898faf491ea5bbe4b0c442a28de9b617d5
Timestamp: 1747177085 Timestamp [UCT]: 2025-05-13 22:58:05 Age [y:d:h:m:s]: 00:147:21:00:24
Block: 1282334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103331 RingCT/type: yes/0
Extra: 0118245e6f46ed7c69b273613461206d898faf491ea5bbe4b0c442a28de9b617d50211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63cffdb65ea7e3b8fa27a095b1411e221e1f2c7fc81c7febce5617590951aaa8 0.600000000000 1769741 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": 1282344, "vin": [ { "gen": { "height": 1282334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63cffdb65ea7e3b8fa27a095b1411e221e1f2c7fc81c7febce5617590951aaa8" } } ], "extra": [ 1, 24, 36, 94, 111, 70, 237, 124, 105, 178, 115, 97, 52, 97, 32, 109, 137, 143, 175, 73, 30, 165, 187, 228, 176, 196, 66, 162, 141, 233, 182, 23, 213, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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