Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c20b00230f2b5c83c75701be44ad20dd09b148074efbcb2946b2f4833d54244b

Tx prefix hash: c7c4f3487c40ad472c1c72975b94c33172a9c1f8741ad41e97cb1f1e21f8591e
Tx public key: a84279a64565e082c3db48a52f7a9083aa28ce278cf2d4aa01c64eb9d6878b58
Timestamp: 1702578110 Timestamp [UCT]: 2023-12-14 18:21:50 Age [y:d:h:m:s]: 01:149:17:08:47
Block: 913118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368158 RingCT/type: yes/0
Extra: 01a84279a64565e082c3db48a52f7a9083aa28ce278cf2d4aa01c64eb9d6878b5802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c047b7baca0b2723b1e98ce83c5417e435a17d3bcf87bf38427f60bc547918e7 0.600000000000 1370364 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": 913128, "vin": [ { "gen": { "height": 913118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c047b7baca0b2723b1e98ce83c5417e435a17d3bcf87bf38427f60bc547918e7" } } ], "extra": [ 1, 168, 66, 121, 166, 69, 101, 224, 130, 195, 219, 72, 165, 47, 122, 144, 131, 170, 40, 206, 39, 140, 242, 212, 170, 1, 198, 78, 185, 214, 135, 139, 88, 2, 17, 0, 0, 0, 6, 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