Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71e0a84a4c8b59f2ea8488c3bb44a753d126145f244aab7d5b3ddc575fbd6b83

Tx prefix hash: 3577703334cc2f30695743bbca076f8038e440f1928968923e1e43d9f7339b8c
Tx public key: 9eba8971ae57dba2191b354b25fb82f4482d371d4c3cf3ecc646f02b17cbc1bd
Timestamp: 1737509345 Timestamp [UCT]: 2025-01-22 01:29:05 Age [y:d:h:m:s]: 00:149:16:03:12
Block: 1202523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106671 RingCT/type: yes/0
Extra: 019eba8971ae57dba2191b354b25fb82f4482d371d4c3cf3ecc646f02b17cbc1bd021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 507b5c892d66246bea708fa2f74dae197ada2e0e119eb5494f87f1f49863e457 0.600000000000 1689188 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": 1202533, "vin": [ { "gen": { "height": 1202523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "507b5c892d66246bea708fa2f74dae197ada2e0e119eb5494f87f1f49863e457" } } ], "extra": [ 1, 158, 186, 137, 113, 174, 87, 219, 162, 25, 27, 53, 75, 37, 251, 130, 244, 72, 45, 55, 29, 76, 60, 243, 236, 198, 70, 240, 43, 23, 203, 193, 189, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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