Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dead9a4db3b012e1a814a0104ff9c2cdae04187a53a9ac8b40c14e2630ad726e

Tx prefix hash: 54eda607b4006b6496c555fb5e683362f6d72e071c987d80f4a47cfb361970e6
Tx public key: 81aaa0a72f06dcf6579943986df72486422bd6b8342680fc4fa254a58f15b4e2
Timestamp: 1685390191 Timestamp [UCT]: 2023-05-29 19:56:31 Age [y:d:h:m:s]: 02:012:13:54:19
Block: 770878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 531100 RingCT/type: yes/0
Extra: 0181aaa0a72f06dcf6579943986df72486422bd6b8342680fc4fa254a58f15b4e202110000000575e3f0e9000000000000000000

1 output(s) for total of 1.713015734000 dcy

stealth address amount amount idx
00: cff0f6597523c18d7c8b89e44dc062c324ba2c6656bac26c9f6be7b4fd727403 1.713015734000 1220211 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": 770888, "vin": [ { "gen": { "height": 770878 } } ], "vout": [ { "amount": 1713015734, "target": { "key": "cff0f6597523c18d7c8b89e44dc062c324ba2c6656bac26c9f6be7b4fd727403" } } ], "extra": [ 1, 129, 170, 160, 167, 47, 6, 220, 246, 87, 153, 67, 152, 109, 247, 36, 134, 66, 43, 214, 184, 52, 38, 128, 252, 79, 162, 84, 165, 143, 21, 180, 226, 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