Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11b8fda8488149c40a5efc5f08a5c7899c2cb43dd5c114bb4e21f6a330e18f0c

Tx prefix hash: 50d32ac0b174ba1121417370395094a96b43e50a6616836be32737c2bd25065c
Tx public key: dd1748d3d0a742f8dc38bfad6a33ee3c203631be9f43e5ade7bff128b4c5839a
Timestamp: 1723862759 Timestamp [UCT]: 2024-08-17 02:45:59 Age [y:d:h:m:s]: 00:247:06:43:23
Block: 1089579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176610 RingCT/type: yes/0
Extra: 01dd1748d3d0a742f8dc38bfad6a33ee3c203631be9f43e5ade7bff128b4c5839a021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5ce73aa326adf58e8c57797dfb219791bcf09d9ae5688d7724f4f453e66ddff 0.600000000000 1564202 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": 1089589, "vin": [ { "gen": { "height": 1089579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5ce73aa326adf58e8c57797dfb219791bcf09d9ae5688d7724f4f453e66ddff" } } ], "extra": [ 1, 221, 23, 72, 211, 208, 167, 66, 248, 220, 56, 191, 173, 106, 51, 238, 60, 32, 54, 49, 190, 159, 67, 229, 173, 231, 191, 241, 40, 180, 197, 131, 154, 2, 17, 0, 0, 0, 4, 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