Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9df5a42ef270d5e7aa6f21c6224c07cb9f461fdd4f7552e489570d357b8e9c

Tx prefix hash: 7de18fc67051ec9e9e3be539240dfdd3399d362cebd7116cea2da5683a7c5885
Tx public key: 2b3289f869acfa937d29e573a961b481c301551ec91b60aa39cefa52f9c191dc
Timestamp: 1723868846 Timestamp [UCT]: 2024-08-17 04:27:26 Age [y:d:h:m:s]: 00:249:16:05:00
Block: 1089634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178317 RingCT/type: yes/0
Extra: 012b3289f869acfa937d29e573a961b481c301551ec91b60aa39cefa52f9c191dc02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc08ed92ea080f6ae0e6ff6f033d4161c6266cacf2ded44d709bb6449f5be77c 0.600000000000 1564257 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": 1089644, "vin": [ { "gen": { "height": 1089634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc08ed92ea080f6ae0e6ff6f033d4161c6266cacf2ded44d709bb6449f5be77c" } } ], "extra": [ 1, 43, 50, 137, 248, 105, 172, 250, 147, 125, 41, 229, 115, 169, 97, 180, 129, 195, 1, 85, 30, 201, 27, 96, 170, 57, 206, 250, 82, 249, 193, 145, 220, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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