Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfdc92314a10726d1801ec50ba85fe238f8abab32e4a778ba45b0c2a7920eeb5

Tx prefix hash: 26fbed1646d9c01dff2911f51b9ec8b1ffcfa52ea7dde15af19a7e5bc4d9af3e
Tx public key: d44138c28987dbd4ac6210a61b34fb4daf02ee8dedc209909b1fa42c5f4a333f
Timestamp: 1723798967 Timestamp [UCT]: 2024-08-16 09:02:47 Age [y:d:h:m:s]: 00:303:19:14:47
Block: 1089046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216954 RingCT/type: yes/0
Extra: 01d44138c28987dbd4ac6210a61b34fb4daf02ee8dedc209909b1fa42c5f4a333f02110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b60f3572d12fa09a915d63c6f5e443427727f1ac18961ab1f53168fa109e398 0.600000000000 1563665 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": 1089056, "vin": [ { "gen": { "height": 1089046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b60f3572d12fa09a915d63c6f5e443427727f1ac18961ab1f53168fa109e398" } } ], "extra": [ 1, 212, 65, 56, 194, 137, 135, 219, 212, 172, 98, 16, 166, 27, 52, 251, 77, 175, 2, 238, 141, 237, 194, 9, 144, 155, 31, 164, 44, 95, 74, 51, 63, 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