Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a816f5cf3c847d4ff411520ec4d7ae92acf2fef9ef7c1384eecc2161506c7d2

Tx prefix hash: 33e286bf27db70b0084d5f37c750fdbbe4ecf261b6c2891ecbd920697d859bcf
Tx public key: 994e4d06e479d778fa879dd070aa3ad76c8f7fa90acec1ccaad0d4632855f69f
Timestamp: 1733631774 Timestamp [UCT]: 2024-12-08 04:22:54 Age [y:d:h:m:s]: 00:137:20:27:21
Block: 1170471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98330 RingCT/type: yes/0
Extra: 01994e4d06e479d778fa879dd070aa3ad76c8f7fa90acec1ccaad0d4632855f69f021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac45b8a8d37e7b6a4e52e86dfe79d695b1457138cd47351c5be7c0fd1c0f3bda 0.600000000000 1656202 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": 1170481, "vin": [ { "gen": { "height": 1170471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac45b8a8d37e7b6a4e52e86dfe79d695b1457138cd47351c5be7c0fd1c0f3bda" } } ], "extra": [ 1, 153, 78, 77, 6, 228, 121, 215, 120, 250, 135, 157, 208, 112, 170, 58, 215, 108, 143, 127, 169, 10, 206, 193, 204, 170, 208, 212, 99, 40, 85, 246, 159, 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