Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fb52b4d02a1cc87784130923feed29bfd5437f9dfeb60a1759b630629e8dfe7

Tx prefix hash: 6d09925a27bdabaf4e33d4b24fb547a9dfd9419123f93ddfd8f48fb2017d0dad
Tx public key: 50d20a79ffe5f18379e2183a2111f5e54953425b4fd66a65e8dffd3e66af4e94
Timestamp: 1736775160 Timestamp [UCT]: 2025-01-13 13:32:40 Age [y:d:h:m:s]: 00:155:06:00:10
Block: 1196490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110660 RingCT/type: yes/0
Extra: 0150d20a79ffe5f18379e2183a2111f5e54953425b4fd66a65e8dffd3e66af4e94021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d96992e1810ba46b17a8a95a90f658adb4826ee1e518980db28fdff3f34cebd4 0.600000000000 1683089 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": 1196500, "vin": [ { "gen": { "height": 1196490 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d96992e1810ba46b17a8a95a90f658adb4826ee1e518980db28fdff3f34cebd4" } } ], "extra": [ 1, 80, 210, 10, 121, 255, 229, 241, 131, 121, 226, 24, 58, 33, 17, 245, 229, 73, 83, 66, 91, 79, 214, 106, 101, 232, 223, 253, 62, 102, 175, 78, 148, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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