Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b31135ca41a11241a436ec2af8395664146df3f6eef2b93e7b762c18709e1e2

Tx prefix hash: bb7d4d560ff7cac89bb9c4addfe2e0ac5712b6b11870ce397cbf4729cc11dad0
Tx public key: f41216b12c5711968ca26e733e1f66cb9f6410ce9edd1b1baf6b169c4f4791d7
Timestamp: 1745123462 Timestamp [UCT]: 2025-04-20 04:31:02 Age [y:d:h:m:s]: 00:213:09:41:32
Block: 1265323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150248 RingCT/type: yes/0
Extra: 01f41216b12c5711968ca26e733e1f66cb9f6410ce9edd1b1baf6b169c4f4791d70211000000096c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ea35b9f8a79afac44e5ba2133f76f194f5bb134397858c7a75ee55cd451f1ec 0.600000000000 1752530 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": 1265333, "vin": [ { "gen": { "height": 1265323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ea35b9f8a79afac44e5ba2133f76f194f5bb134397858c7a75ee55cd451f1ec" } } ], "extra": [ 1, 244, 18, 22, 177, 44, 87, 17, 150, 140, 162, 110, 115, 62, 31, 102, 203, 159, 100, 16, 206, 158, 221, 27, 27, 175, 107, 22, 156, 79, 71, 145, 215, 2, 17, 0, 0, 0, 9, 108, 152, 170, 61, 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