Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53007a18d932ad88ab666cacb0d79997082ac1d2c373e05a17fa739e729e149b

Tx prefix hash: fee361e0f77249ea9305a15fe72d7e8a1d0a3bcbf978440aff810e5a7e54ab89
Tx public key: 0e7337f3b9bb7275e73ef86faaf7c2cf9cc16800d119bc1eda4ced9f3b9ecb69
Timestamp: 1697909730 Timestamp [UCT]: 2023-10-21 17:35:30 Age [y:d:h:m:s]: 01:159:14:55:07
Block: 874620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375093 RingCT/type: yes/0
Extra: 010e7337f3b9bb7275e73ef86faaf7c2cf9cc16800d119bc1eda4ced9f3b9ecb69021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.776284453000 dcy

stealth address amount amount idx
00: a0cf04a1ff6fd43bc1fe24a38b108fcc4e955514b3adeb925e5ca92527751599 0.776284453000 1329842 of 0

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": 874630, "vin": [ { "gen": { "height": 874620 } } ], "vout": [ { "amount": 776284453, "target": { "key": "a0cf04a1ff6fd43bc1fe24a38b108fcc4e955514b3adeb925e5ca92527751599" } } ], "extra": [ 1, 14, 115, 55, 243, 185, 187, 114, 117, 231, 62, 248, 111, 170, 247, 194, 207, 156, 193, 104, 0, 209, 25, 188, 30, 218, 76, 237, 159, 59, 158, 203, 105, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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