Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779a39a5ae806c332d7b254366169c9cbe4d89a327ff6a6022b15d6aa21c46b1

Tx prefix hash: 0ae71b7a7210fe3b057f5de125044db2702384f5f3e8dcedd60552de605a9187
Tx public key: 42b2c60a78bcc4fd96a9b7a7f9c2fe09cbbe49f4cd8a16dc5cf3b49ac795d30e
Timestamp: 1738213502 Timestamp [UCT]: 2025-01-30 05:05:02 Age [y:d:h:m:s]: 00:320:17:16:13
Block: 1208131 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227010 RingCT/type: yes/0
Extra: 0142b2c60a78bcc4fd96a9b7a7f9c2fe09cbbe49f4cd8a16dc5cf3b49ac795d30e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 673c8a4653fdd595ae25d1eb0a4157e634675ee32c96659e99d334f57ef0b873 0.600000000000 1694860 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": 1208141, "vin": [ { "gen": { "height": 1208131 } } ], "vout": [ { "amount": 600000000, "target": { "key": "673c8a4653fdd595ae25d1eb0a4157e634675ee32c96659e99d334f57ef0b873" } } ], "extra": [ 1, 66, 178, 198, 10, 120, 188, 196, 253, 150, 169, 183, 167, 249, 194, 254, 9, 203, 190, 73, 244, 205, 138, 22, 220, 92, 243, 180, 154, 199, 149, 211, 14, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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