Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f93fb8ffa89e5ad490e116c09833b7b1ce7d504f8dbebeed251bfb3198e71c9

Tx prefix hash: b407531abaec9949ef0bce8e41bfacc498faefe08a413861b1564f87f3b7d48a
Tx public key: fe3aaaf1d8b958e0ca5d9cf8d55af77741a6070e2fd1dc399501dba564c37158
Timestamp: 1745038950 Timestamp [UCT]: 2025-04-19 05:02:30 Age [y:d:h:m:s]: 00:019:05:36:50
Block: 1264630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13767 RingCT/type: yes/0
Extra: 01fe3aaaf1d8b958e0ca5d9cf8d55af77741a6070e2fd1dc399501dba564c37158021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a30d60a87f3641476034f1e294158eb5a51a8d78c3ec01b0838421425762bfa 0.600000000000 1751829 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": 1264640, "vin": [ { "gen": { "height": 1264630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a30d60a87f3641476034f1e294158eb5a51a8d78c3ec01b0838421425762bfa" } } ], "extra": [ 1, 254, 58, 170, 241, 216, 185, 88, 224, 202, 93, 156, 248, 213, 90, 247, 119, 65, 166, 7, 14, 47, 209, 220, 57, 149, 1, 219, 165, 100, 195, 113, 88, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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