Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34c367491143e36807f683ed2d22342b0f99af3e8cec5b35dfe3ae8d0bed085a

Tx prefix hash: 31384d4cbf729a77aa7bb70c327b8becf336e5a088f75f37e91a0790da3a63de
Tx public key: 1021675f8c30c6eb1cdac55aa1e5b6cf344bdf43f1c4419d87c031d43f952134
Timestamp: 1733330689 Timestamp [UCT]: 2024-12-04 16:44:49 Age [y:d:h:m:s]: 00:119:09:52:58
Block: 1167967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85139 RingCT/type: yes/0
Extra: 011021675f8c30c6eb1cdac55aa1e5b6cf344bdf43f1c4419d87c031d43f952134021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f16860f9708918400a39d64ed27f12caf4a55e644855a1bf96f7b73fe27a091 0.600000000000 1653672 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": 1167977, "vin": [ { "gen": { "height": 1167967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f16860f9708918400a39d64ed27f12caf4a55e644855a1bf96f7b73fe27a091" } } ], "extra": [ 1, 16, 33, 103, 95, 140, 48, 198, 235, 28, 218, 197, 90, 161, 229, 182, 207, 52, 75, 223, 67, 241, 196, 65, 157, 135, 192, 49, 212, 63, 149, 33, 52, 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