Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5415a10d6d739133327bd6dd72d3f3586eb8aad14df42431ed1ec49d639955

Tx prefix hash: bea26b4c60eee56ac20fcb247266d72e622b680f133e9d45382508bdf3d525a4
Tx public key: 923f1971d8cf3f03d7d9985f83958b8a24bc6cd7b2e6f178310e3465bfa82cd5
Timestamp: 1754313850 Timestamp [UCT]: 2025-08-04 13:24:10 Age [y:d:h:m:s]: 00:107:18:37:19
Block: 1340116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75989 RingCT/type: yes/0
Extra: 01923f1971d8cf3f03d7d9985f83958b8a24bc6cd7b2e6f178310e3465bfa82cd5021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e9b703f0c5b6dc6f58a83960b55f3e51a598d7a4464f46402302eace60064fb 0.600000000000 1827933 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": 1340126, "vin": [ { "gen": { "height": 1340116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e9b703f0c5b6dc6f58a83960b55f3e51a598d7a4464f46402302eace60064fb" } } ], "extra": [ 1, 146, 63, 25, 113, 216, 207, 63, 3, 215, 217, 152, 95, 131, 149, 139, 138, 36, 188, 108, 215, 178, 230, 241, 120, 49, 14, 52, 101, 191, 168, 44, 213, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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