Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 829a052a60ff62b6729348cdbdffad0f9e2b58e62b4630a1e2d5a0222c65593d

Tx prefix hash: 9ad31b07456d0d6a9ba5a22efd36ca1d42948d73e99e2b09360bec46e448e703
Tx public key: 89466305ef7f7ec04c5d6fefb55a9bc7ec5fcb12a859fb73a39cb4150c3097f1
Timestamp: 1751521391 Timestamp [UCT]: 2025-07-03 05:43:11 Age [y:d:h:m:s]: 00:140:21:47:28
Block: 1317735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98936 RingCT/type: yes/0
Extra: 0189466305ef7f7ec04c5d6fefb55a9bc7ec5fcb12a859fb73a39cb4150c3097f1021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b5af9f02f8def0b3fdae1aaa110af3b28ffb78ea3be00f62d46f7ed9754359d 0.600000000000 1805404 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": 1317745, "vin": [ { "gen": { "height": 1317735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b5af9f02f8def0b3fdae1aaa110af3b28ffb78ea3be00f62d46f7ed9754359d" } } ], "extra": [ 1, 137, 70, 99, 5, 239, 127, 126, 192, 76, 93, 111, 239, 181, 90, 155, 199, 236, 95, 203, 18, 168, 89, 251, 115, 163, 156, 180, 21, 12, 48, 151, 241, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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