Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7460352fde65f38dc013c620a45abfa03813e7d3e470ce63685aa069fe7d7648

Tx prefix hash: ae86b50f1596d2e713b3d0614702e6864c0ef55878d39f56283b62e62e1b9d97
Tx public key: d504a00af0d7c786cc7420a3cf79c4543b0415cc7a466e9dedab7fcc10ca9b85
Timestamp: 1745210838 Timestamp [UCT]: 2025-04-21 04:47:18 Age [y:d:h:m:s]: 00:023:15:43:54
Block: 1266038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 16946 RingCT/type: yes/0
Extra: 01d504a00af0d7c786cc7420a3cf79c4543b0415cc7a466e9dedab7fcc10ca9b850211000000056c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6261c37b75008528e278a54c157592e8491339f9b7f53a338a11616c410fcc7f 0.600000000000 1753253 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": 1266048, "vin": [ { "gen": { "height": 1266038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6261c37b75008528e278a54c157592e8491339f9b7f53a338a11616c410fcc7f" } } ], "extra": [ 1, 213, 4, 160, 10, 240, 215, 199, 134, 204, 116, 32, 163, 207, 121, 196, 84, 59, 4, 21, 204, 122, 70, 110, 157, 237, 171, 127, 204, 16, 202, 155, 133, 2, 17, 0, 0, 0, 5, 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