Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 261a18d02476554fc867efd20eb2e0c76259f494c44436a4c7bfc35c2effab2c

Tx prefix hash: c3553a3757a0c47f72d735f5066c6bfb4bd0654ce521b5d64af94168c015bbac
Tx public key: 2e244125434279a23f7f0e670bbcc734c9a504e8b653cc8a8284494f6a2ff8a3
Timestamp: 1675004954 Timestamp [UCT]: 2023-01-29 15:09:14 Age [y:d:h:m:s]: 02:116:11:14:06
Block: 685417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 604896 RingCT/type: yes/0
Extra: 012e244125434279a23f7f0e670bbcc734c9a504e8b653cc8a8284494f6a2ff8a302110000000175e3f0e9000000000000000000

1 output(s) for total of 3.287977853000 dcy

stealth address amount amount idx
00: 9ea1a1956e3213bb4fff5c130ea46c4e413832551074d254118df26b8a1da7df 3.287977853000 1127734 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": 685427, "vin": [ { "gen": { "height": 685417 } } ], "vout": [ { "amount": 3287977853, "target": { "key": "9ea1a1956e3213bb4fff5c130ea46c4e413832551074d254118df26b8a1da7df" } } ], "extra": [ 1, 46, 36, 65, 37, 67, 66, 121, 162, 63, 127, 14, 103, 11, 188, 199, 52, 201, 165, 4, 232, 182, 83, 204, 138, 130, 132, 73, 79, 106, 47, 248, 163, 2, 17, 0, 0, 0, 1, 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