Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38007a7e5239c6fa6190ccbc32e110d64f4568f573de3dc4d0b59d27e92f7323

Tx prefix hash: f4bb8793336efcce6d49d5be9ee260b49ee93a87b53e3b08618646246d377c74
Tx public key: b637f27bc61cbb8eb0e5b29b20e3e36b584a5e629f1f359bcc71e71dd8b412e5
Timestamp: 1763283338 Timestamp [UCT]: 2025-11-16 08:55:38 Age [y:d:h:m:s]: 00:036:23:32:19
Block: 1413268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26481 RingCT/type: yes/0
Extra: 01b637f27bc61cbb8eb0e5b29b20e3e36b584a5e629f1f359bcc71e71dd8b412e502110000000417b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 83a09bf0f87d5d9094224d8a7ea14362cfbd4ddd6997416e1955de6ce01c8e05 0.600000000000 1901745 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": 1413278, "vin": [ { "gen": { "height": 1413268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "83a09bf0f87d5d9094224d8a7ea14362cfbd4ddd6997416e1955de6ce01c8e05" } } ], "extra": [ 1, 182, 55, 242, 123, 198, 28, 187, 142, 176, 229, 178, 155, 32, 227, 227, 107, 88, 74, 94, 98, 159, 31, 53, 155, 204, 113, 231, 29, 216, 180, 18, 229, 2, 17, 0, 0, 0, 4, 23, 177, 145, 50, 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