Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2b170c1e8258e165eacad00c1f3ed334bfbe259e3f37081c952770648d0147a

Tx prefix hash: 73ee8ea6ba7363ccd69a719bebc876353d1dc88c536fd69623b282a9073e4ada
Tx public key: 59ca2ae085e2620a511f763b719286a53b70672211dd9f2dd4c6085bec182b79
Timestamp: 1695240759 Timestamp [UCT]: 2023-09-20 20:12:39 Age [y:d:h:m:s]: 01:160:17:00:45
Block: 852479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375914 RingCT/type: yes/0
Extra: 0159ca2ae085e2620a511f763b719286a53b70672211dd9f2dd4c6085bec182b7902110000000575e3f0e9000000000000000000

1 output(s) for total of 0.919143341000 dcy

stealth address amount amount idx
00: 38cf8dc00c07d42598a064a8630560ac5fa1aa89ac764fdfc718154b378c2b90 0.919143341000 1306321 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": 852489, "vin": [ { "gen": { "height": 852479 } } ], "vout": [ { "amount": 919143341, "target": { "key": "38cf8dc00c07d42598a064a8630560ac5fa1aa89ac764fdfc718154b378c2b90" } } ], "extra": [ 1, 89, 202, 42, 224, 133, 226, 98, 10, 81, 31, 118, 59, 113, 146, 134, 165, 59, 112, 103, 34, 17, 221, 159, 45, 212, 198, 8, 91, 236, 24, 43, 121, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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