Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6508d7608f12bdd909ac259714df9461a8a6b406729208d629c4dc3dde907b0

Tx prefix hash: ba68762e2f577feaf73f19b44637eb869a3a4fcf57d6be66bcd2bb8dab89362f
Tx public key: 3b2115b89ec614c12495989d44f8af626cfe0f034d3f4ddde20e22d586e78bd8
Timestamp: 1715781013 Timestamp [UCT]: 2024-05-15 13:50:13 Age [y:d:h:m:s]: 00:305:13:08:48
Block: 1022579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218396 RingCT/type: yes/0
Extra: 013b2115b89ec614c12495989d44f8af626cfe0f034d3f4ddde20e22d586e78bd80211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6208bc8f0bbe563a6a95d0fea3862ab2a31593731fce3f17fe219fbe93c209ac 0.600000000000 1487224 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": 1022589, "vin": [ { "gen": { "height": 1022579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6208bc8f0bbe563a6a95d0fea3862ab2a31593731fce3f17fe219fbe93c209ac" } } ], "extra": [ 1, 59, 33, 21, 184, 158, 198, 20, 193, 36, 149, 152, 157, 68, 248, 175, 98, 108, 254, 15, 3, 77, 63, 77, 221, 226, 14, 34, 213, 134, 231, 139, 216, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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