Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5caa98595e52d6b2c6965ed246b493c474ede75f4c54ff91d3f12666938c293

Tx prefix hash: 4a79de377fefc0b56d2e6c3bdafc08f48b5d9f34f50677f88717217fc71a008d
Tx public key: c9809271a414b946d4a43dbd2ed94ceb7d7eea2f1fb43e869481c12c1371e541
Timestamp: 1706365447 Timestamp [UCT]: 2024-01-27 14:24:07 Age [y:d:h:m:s]: 00:308:19:07:11
Block: 944495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221118 RingCT/type: yes/0
Extra: 01c9809271a414b946d4a43dbd2ed94ceb7d7eea2f1fb43e869481c12c1371e54102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 590c91b369a5356da87158440d2ce8871371491adb6210a789267ea9f352d576 0.600000000000 1402747 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": 944505, "vin": [ { "gen": { "height": 944495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "590c91b369a5356da87158440d2ce8871371491adb6210a789267ea9f352d576" } } ], "extra": [ 1, 201, 128, 146, 113, 164, 20, 185, 70, 212, 164, 61, 189, 46, 217, 76, 235, 125, 126, 234, 47, 31, 180, 62, 134, 148, 129, 193, 44, 19, 113, 229, 65, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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