Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d926526188fd20a54531849db5a507d1d2d796e724e473ab2ecea400b3b3d845

Tx prefix hash: 932bbe0fbef26abb110a83f769bd2664ccbb844e9f47524db185ef112b67e84e
Tx public key: bc7250fda56c5b7a0a1d737f3dcb72cec8fe459c327811e8684f5789c881b12a
Timestamp: 1720492550 Timestamp [UCT]: 2024-07-09 02:35:50 Age [y:d:h:m:s]: 00:129:01:36:55
Block: 1061647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92346 RingCT/type: yes/0
Extra: 01bc7250fda56c5b7a0a1d737f3dcb72cec8fe459c327811e8684f5789c881b12a0211000000045ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0292395cd13fca9f2b921a1ba151ef77b4efa8c2b67082ab99bb90f55547019 0.600000000000 1532140 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": 1061657, "vin": [ { "gen": { "height": 1061647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0292395cd13fca9f2b921a1ba151ef77b4efa8c2b67082ab99bb90f55547019" } } ], "extra": [ 1, 188, 114, 80, 253, 165, 108, 91, 122, 10, 29, 115, 127, 61, 203, 114, 206, 200, 254, 69, 156, 50, 120, 17, 232, 104, 79, 87, 137, 200, 129, 177, 42, 2, 17, 0, 0, 0, 4, 95, 241, 21, 127, 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