Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b2851e7a26a6c5a8dd3bd7962fc7d913695f3ba1757a980f33171ca8b07bfee

Tx prefix hash: 345c11adb5693ddeff0d2e07ef0af064ad620a5db70b07c549105cfdfdb331ab
Tx public key: e3a79c69bf24a62aef18ad102c5a5613bef7a520eb863ab05ad316ab0e524bb5
Timestamp: 1734931279 Timestamp [UCT]: 2024-12-23 05:21:19 Age [y:d:h:m:s]: 00:177:03:41:43
Block: 1181252 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126296 RingCT/type: yes/0
Extra: 01e3a79c69bf24a62aef18ad102c5a5613bef7a520eb863ab05ad316ab0e524bb5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb5c624ab8da6d2e78b1e1e360061b07403e285a86cbcd2cee2165aa354f4320 0.600000000000 1667669 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": 1181262, "vin": [ { "gen": { "height": 1181252 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb5c624ab8da6d2e78b1e1e360061b07403e285a86cbcd2cee2165aa354f4320" } } ], "extra": [ 1, 227, 167, 156, 105, 191, 36, 166, 42, 239, 24, 173, 16, 44, 90, 86, 19, 190, 247, 165, 32, 235, 134, 58, 176, 90, 211, 22, 171, 14, 82, 75, 181, 2, 17, 0, 0, 0, 4, 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