Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b388ebfe2d1b205a6fdade70b453aebcca6eb3ac6c8a34280b646cace3fb1a93

Tx prefix hash: fbe4dbc5dfb8e316a4f0e1b037feb57c9757fedc37e2ead12e01dc4c92622ed2
Tx public key: 97dcf343fac4129e3f633be93f96cd4d768e8b6cfeed9dac196120dee41934e6
Timestamp: 1724946593 Timestamp [UCT]: 2024-08-29 15:49:53 Age [y:d:h:m:s]: 00:259:06:08:50
Block: 1098560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185170 RingCT/type: yes/0
Extra: 0197dcf343fac4129e3f633be93f96cd4d768e8b6cfeed9dac196120dee41934e602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b18cf2c52065caf27e4c4bdfd05043e0e5cfca217ea157e5c7f91090d10e58c8 0.600000000000 1574317 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": 1098570, "vin": [ { "gen": { "height": 1098560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b18cf2c52065caf27e4c4bdfd05043e0e5cfca217ea157e5c7f91090d10e58c8" } } ], "extra": [ 1, 151, 220, 243, 67, 250, 196, 18, 158, 63, 99, 59, 233, 63, 150, 205, 77, 118, 142, 139, 108, 254, 237, 157, 172, 25, 97, 32, 222, 228, 25, 52, 230, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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