Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7fb5007e52fe1b0cb50c8791135c0440b1520b5fa15afa9b537a028812cfd63

Tx prefix hash: 6b8209349b7cd934697d6ec30be90d94a6a056ef806d940a181da890c682bb1a
Tx public key: df504fcd54adb2802fc8f03f3cf28b1ae906e919b6b308b10f58fe740a068693
Timestamp: 1726659199 Timestamp [UCT]: 2024-09-18 11:33:19 Age [y:d:h:m:s]: 00:198:04:49:53
Block: 1112763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141478 RingCT/type: yes/0
Extra: 01df504fcd54adb2802fc8f03f3cf28b1ae906e919b6b308b10f58fe740a068693021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5e7a7b17351348b2fe23c231e77a6b5ab765453cd59289bd7c69a60622607d2 0.600000000000 1592198 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": 1112773, "vin": [ { "gen": { "height": 1112763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5e7a7b17351348b2fe23c231e77a6b5ab765453cd59289bd7c69a60622607d2" } } ], "extra": [ 1, 223, 80, 79, 205, 84, 173, 178, 128, 47, 200, 240, 63, 60, 242, 139, 26, 233, 6, 233, 25, 182, 179, 8, 177, 15, 88, 254, 116, 10, 6, 134, 147, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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