Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eba03502baf438b4c14d9737290c4c690677c5fa83a20c39e562448ba53bc76d

Tx prefix hash: 536aae3f9700d1c1a9cb027f50c33b5ac783b0b671667294b12348204d65c578
Tx public key: 0a6d6b8042a13b09af4f97e2120740ac590629c810a45ccdf68ea0bcf4c61e15
Timestamp: 1708830666 Timestamp [UCT]: 2024-02-25 03:11:06 Age [y:d:h:m:s]: 01:060:10:52:23
Block: 964958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304243 RingCT/type: yes/0
Extra: 010a6d6b8042a13b09af4f97e2120740ac590629c810a45ccdf68ea0bcf4c61e1502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8f20fe4af40be4ede548f3a29100ef690938eb5a671e402137fa1e2965f8b36 0.600000000000 1424701 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": 964968, "vin": [ { "gen": { "height": 964958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8f20fe4af40be4ede548f3a29100ef690938eb5a671e402137fa1e2965f8b36" } } ], "extra": [ 1, 10, 109, 107, 128, 66, 161, 59, 9, 175, 79, 151, 226, 18, 7, 64, 172, 89, 6, 41, 200, 16, 164, 92, 205, 246, 142, 160, 188, 244, 198, 30, 21, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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