Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829b70a2adb90d7e1755230ed3ad52cee6a37ebd66d08da3f7c30bd5776ca8a9

Tx prefix hash: 07231f39a43e5e65c320b39eab2596fd375554b1677274e6ddcd7f7b2a6d8378
Tx public key: 065aec2c4e658cb3d6c5dc760364513fc15eea64d3aa49af27b1506620104f30
Timestamp: 1722783043 Timestamp [UCT]: 2024-08-04 14:50:43 Age [y:d:h:m:s]: 00:247:06:04:50
Block: 1080621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176608 RingCT/type: yes/0
Extra: 01065aec2c4e658cb3d6c5dc760364513fc15eea64d3aa49af27b1506620104f3002110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a9d366931469573c888246208cd2ceb8046df144eaa553f9d183679df186aa5 0.600000000000 1554056 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": 1080631, "vin": [ { "gen": { "height": 1080621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a9d366931469573c888246208cd2ceb8046df144eaa553f9d183679df186aa5" } } ], "extra": [ 1, 6, 90, 236, 44, 78, 101, 140, 179, 214, 197, 220, 118, 3, 100, 81, 63, 193, 94, 234, 100, 211, 170, 73, 175, 39, 177, 80, 102, 32, 16, 79, 48, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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