Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6381849cea6c1272766a2caff7330fe295834b7dad67c752c065d9de61b750b9

Tx prefix hash: 31dfe33e1211f3c8378d42fb2b06eca8ae5915c83a643fa1e771d3c82232b8ab
Tx public key: 23a5b5c38153fa8843f14d9aba970b84978d0ad8a908cdd2b43006bd24859fdf
Timestamp: 1760475591 Timestamp [UCT]: 2025-10-14 20:59:51 Age [y:d:h:m:s]: 00:026:22:45:51
Block: 1389999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19299 RingCT/type: yes/0
Extra: 0123a5b5c38153fa8843f14d9aba970b84978d0ad8a908cdd2b43006bd24859fdf021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf6ddef746dbef5d2c32ce843504b975c61a1b3d6f7519fbf1e2d6618c4aa8f4 0.600000000000 1878230 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": 1390009, "vin": [ { "gen": { "height": 1389999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf6ddef746dbef5d2c32ce843504b975c61a1b3d6f7519fbf1e2d6618c4aa8f4" } } ], "extra": [ 1, 35, 165, 181, 195, 129, 83, 250, 136, 67, 241, 77, 154, 186, 151, 11, 132, 151, 141, 10, 216, 169, 8, 205, 210, 180, 48, 6, 189, 36, 133, 159, 223, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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