Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31f97ac54062363378e0e0cc7a003c5c4eda7dc1f48d9215760e8eb8259254d6

Tx prefix hash: 6e1f35abc34a2cb74e74c6043358f451191d853c818f04879ca32a1b4a8a8bc3
Tx public key: b2b7a2d73b45cafc178c204a838963b5098e666c63debcb24b770697705fbf4f
Timestamp: 1766221635 Timestamp [UCT]: 2025-12-20 09:07:15 Age [y:d:h:m:s]: 00:001:07:02:45
Block: 1437623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 921 RingCT/type: yes/0
Extra: 01b2b7a2d73b45cafc178c204a838963b5098e666c63debcb24b770697705fbf4f0211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfd16fb5ee6f49d7c62954def3b9c57f84a4c94586d4524ebd29c2da4fb791a9 0.600000000000 1926432 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": 1437633, "vin": [ { "gen": { "height": 1437623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfd16fb5ee6f49d7c62954def3b9c57f84a4c94586d4524ebd29c2da4fb791a9" } } ], "extra": [ 1, 178, 183, 162, 215, 59, 69, 202, 252, 23, 140, 32, 74, 131, 137, 99, 181, 9, 142, 102, 108, 99, 222, 188, 178, 75, 119, 6, 151, 112, 95, 191, 79, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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