Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e29bb2dbab37317c2b142c015dc90d0803847f072a4e7aded4c373c8966c2583

Tx prefix hash: 7701de54de80885b0a53d28869c1186eac3b5a9faa371f96f85ec988aa63865e
Tx public key: 687f746ebde24204281caf08ef13f3ab7ffef0309e5770d6df8cb752e857cf2c
Timestamp: 1714767682 Timestamp [UCT]: 2024-05-03 20:21:22 Age [y:d:h:m:s]: 01:188:10:45:08
Block: 1014182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393303 RingCT/type: yes/0
Extra: 01687f746ebde24204281caf08ef13f3ab7ffef0309e5770d6df8cb752e857cf2c0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfbcd9199fe1a200eac2f523a27f1fcdc77e1fc5254b8d5cc897c4886feb421d 0.600000000000 1477199 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": 1014192, "vin": [ { "gen": { "height": 1014182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfbcd9199fe1a200eac2f523a27f1fcdc77e1fc5254b8d5cc897c4886feb421d" } } ], "extra": [ 1, 104, 127, 116, 110, 189, 226, 66, 4, 40, 28, 175, 8, 239, 19, 243, 171, 127, 254, 240, 48, 158, 87, 112, 214, 223, 140, 183, 82, 232, 87, 207, 44, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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