Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f97d828536c8ffa19d842d1fa410b6f7dc06811c25117ac903b93057f68d84

Tx prefix hash: 11efc448adcfeb4689430be20740444ba9801aa5607a7976088b36b571e237f1
Tx public key: 0a3c056c6b2304042f790d06a4c17b44f35c78f60a87c78ac81c3ed73115cb9f
Timestamp: 1725527310 Timestamp [UCT]: 2024-09-05 09:08:30 Age [y:d:h:m:s]: 00:127:14:32:12
Block: 1103379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91254 RingCT/type: yes/0
Extra: 010a3c056c6b2304042f790d06a4c17b44f35c78f60a87c78ac81c3ed73115cb9f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c20fe2f4c60e078b867c0f0be54e876b3f78e7647152ac0fca9939c7911c4049 0.600000000000 1580186 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": 1103389, "vin": [ { "gen": { "height": 1103379 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c20fe2f4c60e078b867c0f0be54e876b3f78e7647152ac0fca9939c7911c4049" } } ], "extra": [ 1, 10, 60, 5, 108, 107, 35, 4, 4, 47, 121, 13, 6, 164, 193, 123, 68, 243, 92, 120, 246, 10, 135, 199, 138, 200, 28, 62, 215, 49, 21, 203, 159, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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