Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 10d57639285ed4aec2eb89f85d2bf57e9559522a3ccc4f1a55689fcaffa7b995

Tx prefix hash: 25b56079d8af3274066346d1ca5be231bc92f71ebda98b0ef01a9f5545ef9382
Tx public key: 8e1071e66202f6e144a02bca851aad54cb47d5c847bbd9cf4dc1f186e252c347
Timestamp: 1726385058 Timestamp [UCT]: 2024-09-15 07:24:18 Age [y:d:h:m:s]: 00:203:22:49:08
Block: 1110487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145584 RingCT/type: yes/0
Extra: 018e1071e66202f6e144a02bca851aad54cb47d5c847bbd9cf4dc1f186e252c347021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 701ba8627193130715241324ef28a8b0c8d76b1d1b9144fbf3ca705a10ee09be 0.600000000000 1589114 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": 1110497, "vin": [ { "gen": { "height": 1110487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "701ba8627193130715241324ef28a8b0c8d76b1d1b9144fbf3ca705a10ee09be" } } ], "extra": [ 1, 142, 16, 113, 230, 98, 2, 246, 225, 68, 160, 43, 202, 133, 26, 173, 84, 203, 71, 213, 200, 71, 187, 217, 207, 77, 193, 241, 134, 226, 82, 195, 71, 2, 17, 0, 0, 0, 8, 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