Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d817d1a80330ab6ded437455cb4e49c6e6b964f1dc49ddf0443599bf75d73953

Tx prefix hash: a2905f917e27f71ba0833ca53afa7624dfd141d412f9cb65dc051b365a86ea13
Tx public key: 061eab609dbb61e8dc36c27f487993ba1aa3066a763f58c5f37dcf95e2deb38f
Timestamp: 1690832730 Timestamp [UCT]: 2023-07-31 19:45:30 Age [y:d:h:m:s]: 01:154:04:04:32
Block: 816015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371479 RingCT/type: yes/0
Extra: 01061eab609dbb61e8dc36c27f487993ba1aa3066a763f58c5f37dcf95e2deb38f021100000001faf35c9c000000000000000000

1 output(s) for total of 1.213958017000 dcy

stealth address amount amount idx
00: 0d6d5184835066105dc1dde80a42fcecfda1477814741fb6aca490152420e9aa 1.213958017000 1267828 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": 816025, "vin": [ { "gen": { "height": 816015 } } ], "vout": [ { "amount": 1213958017, "target": { "key": "0d6d5184835066105dc1dde80a42fcecfda1477814741fb6aca490152420e9aa" } } ], "extra": [ 1, 6, 30, 171, 96, 157, 187, 97, 232, 220, 54, 194, 127, 72, 121, 147, 186, 26, 163, 6, 106, 118, 63, 88, 197, 243, 125, 207, 149, 226, 222, 179, 143, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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