Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b4f6c27b2d0c5a1ef061acf6318fedfa49aa54afe1963330ab89b5f109fd760

Tx prefix hash: cbef3c1c823a4fac5f8c9633a904a7c55fec267779598c8222feaff350de9a3c
Tx public key: ed3199deb370b8b4378ec5270a58c32a8ab3cb197de7ce637c723ed91785b0ec
Timestamp: 1723334530 Timestamp [UCT]: 2024-08-11 00:02:10 Age [y:d:h:m:s]: 00:230:00:12:33
Block: 1085203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164269 RingCT/type: yes/0
Extra: 01ed3199deb370b8b4378ec5270a58c32a8ab3cb197de7ce637c723ed91785b0ec02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b871dd81c28fae81f7a4b52945048e4d14a2d865d813a4ffd4f852dd5b65ed8 0.600000000000 1559734 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": 1085213, "vin": [ { "gen": { "height": 1085203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b871dd81c28fae81f7a4b52945048e4d14a2d865d813a4ffd4f852dd5b65ed8" } } ], "extra": [ 1, 237, 49, 153, 222, 179, 112, 184, 180, 55, 142, 197, 39, 10, 88, 195, 42, 138, 179, 203, 25, 125, 231, 206, 99, 124, 114, 62, 217, 23, 133, 176, 236, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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