Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc8612b31741257a774ea9fd8b2089a48766fd0be84b82b118cddac44375ea92

Tx prefix hash: 4d41810eacf22237c8917dfd2e86d30184476f248a5f86a2eb8032d56765416a
Tx public key: adf717a92f1da698d584b1e7706b3e455213f4af6c6676c42c6658de65cca680
Timestamp: 1722882098 Timestamp [UCT]: 2024-08-05 18:21:38 Age [y:d:h:m:s]: 00:223:08:37:23
Block: 1081451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159524 RingCT/type: yes/0
Extra: 01adf717a92f1da698d584b1e7706b3e455213f4af6c6676c42c6658de65cca68002110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2950df40de83ab2a5725d7046ca4a7bbed1f0f85f6a6477384dc01ede5a0a8d8 0.600000000000 1555198 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": 1081461, "vin": [ { "gen": { "height": 1081451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2950df40de83ab2a5725d7046ca4a7bbed1f0f85f6a6477384dc01ede5a0a8d8" } } ], "extra": [ 1, 173, 247, 23, 169, 47, 29, 166, 152, 213, 132, 177, 231, 112, 107, 62, 69, 82, 19, 244, 175, 108, 102, 118, 196, 44, 102, 88, 222, 101, 204, 166, 128, 2, 17, 0, 0, 0, 8, 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