Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83bb0583074e04b6774d3b912f1162b0beb28232333710fe14d1c2e0a2354794

Tx prefix hash: cc09750dd29620443a0139dfb58e5bf7e8458adce7f78727bce3ffc2da32c0b4
Tx public key: 825f994e06aab9d9e68ca3ebb8831db2b1c429dbb549e2376eb7f5e7c5dc4187
Timestamp: 1737788327 Timestamp [UCT]: 2025-01-25 06:58:47 Age [y:d:h:m:s]: 00:144:07:21:42
Block: 1204836 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102861 RingCT/type: yes/0
Extra: 01825f994e06aab9d9e68ca3ebb8831db2b1c429dbb549e2376eb7f5e7c5dc4187021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56e47ef68f88d65a448697faaccc49d0cf14efc9b517efe599198cacf48b4d0f 0.600000000000 1691529 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": 1204846, "vin": [ { "gen": { "height": 1204836 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56e47ef68f88d65a448697faaccc49d0cf14efc9b517efe599198cacf48b4d0f" } } ], "extra": [ 1, 130, 95, 153, 78, 6, 170, 185, 217, 230, 140, 163, 235, 184, 131, 29, 178, 177, 196, 41, 219, 181, 73, 226, 55, 110, 183, 245, 231, 197, 220, 65, 135, 2, 17, 0, 0, 0, 5, 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