Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a9a46f349c635432525e49271d4285c65f9fef95d8521c0892a14bc382c9ee5

Tx prefix hash: 65dd87b6a25bfe6800fd31cc171a8461e5eb1db0be5a51ac341e525a6eb2fba5
Tx public key: 4099b6fbf429fe713189b1ce88f919d7940b137e6c502b214967ed5ebc4dcc8d
Timestamp: 1709120542 Timestamp [UCT]: 2024-02-28 11:42:22 Age [y:d:h:m:s]: 01:099:06:54:12
Block: 967363 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332015 RingCT/type: yes/0
Extra: 014099b6fbf429fe713189b1ce88f919d7940b137e6c502b214967ed5ebc4dcc8d0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d3445a8dc67b809cec7de86f54b83e5a856cf4c4b13da9908974efb6e870cd9 0.600000000000 1427140 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": 967373, "vin": [ { "gen": { "height": 967363 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d3445a8dc67b809cec7de86f54b83e5a856cf4c4b13da9908974efb6e870cd9" } } ], "extra": [ 1, 64, 153, 182, 251, 244, 41, 254, 113, 49, 137, 177, 206, 136, 249, 25, 215, 148, 11, 19, 126, 108, 80, 43, 33, 73, 103, 237, 94, 188, 77, 204, 141, 2, 17, 0, 0, 0, 4, 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