Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbe45e92dd083a4c76c2012b5f946e533fd485d5d5029630a260fa57b7bec13a

Tx prefix hash: 94528d1a7d0c2833e6282f8b11e999328be2a1dea3b0ad2c0541d7467853751a
Tx public key: a7e2b06a050ca2e83a362fec0b6a85ccd509f16934b87bc369d86fb87095b0bd
Timestamp: 1738555889 Timestamp [UCT]: 2025-02-03 04:11:29 Age [y:d:h:m:s]: 00:239:15:03:50
Block: 1210953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168961 RingCT/type: yes/0
Extra: 01a7e2b06a050ca2e83a362fec0b6a85ccd509f16934b87bc369d86fb87095b0bd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f203a84c0b3c714f566ce1963b07e20269f20274712b0d23e2c949e69138ecd5 0.600000000000 1697708 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": 1210963, "vin": [ { "gen": { "height": 1210953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f203a84c0b3c714f566ce1963b07e20269f20274712b0d23e2c949e69138ecd5" } } ], "extra": [ 1, 167, 226, 176, 106, 5, 12, 162, 232, 58, 54, 47, 236, 11, 106, 133, 204, 213, 9, 241, 105, 52, 184, 123, 195, 105, 216, 111, 184, 112, 149, 176, 189, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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