Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81156e4428924bda21488f53a6b151bb6cebc68bcba076b442557bb464c7eb5c

Tx prefix hash: e5086c7f7a2432daf30cf1d9736f654e6cd1ea499e79ff050ddc0bcd2cff4db4
Tx public key: af584d086e69a76a39a96e8527cd95c812cb7462b4c6ccdf1ef26d19fcc96a10
Timestamp: 1749401335 Timestamp [UCT]: 2025-06-08 16:48:55 Age [y:d:h:m:s]: 00:159:07:16:47
Block: 1300757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111532 RingCT/type: yes/0
Extra: 01af584d086e69a76a39a96e8527cd95c812cb7462b4c6ccdf1ef26d19fcc96a10021100000005bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d4189e651a8b0ae8353378030fe245ac51c43eb13cbd4aa8640c4bfba266177 0.600000000000 1788308 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": 1300767, "vin": [ { "gen": { "height": 1300757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d4189e651a8b0ae8353378030fe245ac51c43eb13cbd4aa8640c4bfba266177" } } ], "extra": [ 1, 175, 88, 77, 8, 110, 105, 167, 106, 57, 169, 110, 133, 39, 205, 149, 200, 18, 203, 116, 98, 180, 198, 204, 223, 30, 242, 109, 25, 252, 201, 106, 16, 2, 17, 0, 0, 0, 5, 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