Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdf0e06a08ff0914d623215cfbf532efde3d676dea148d3733a12c564b10e0d1

Tx prefix hash: 12284ab84a7787664a8d5bd8b392cfa1f9ffe501b0c47b8e13ee4038f3586f7d
Tx public key: 8a664748c47032b146f8498c98486128c5b7b4cc3ec1286a1c555253ce46ee52
Timestamp: 1733580594 Timestamp [UCT]: 2024-12-07 14:09:54 Age [y:d:h:m:s]: 00:104:23:08:33
Block: 1170041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74814 RingCT/type: yes/0
Extra: 018a664748c47032b146f8498c98486128c5b7b4cc3ec1286a1c555253ce46ee52021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5df878a09d33742ef0a7e430d0e9a91a0481280c73d6cc5b54c0858e8962a37e 0.600000000000 1655770 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": 1170051, "vin": [ { "gen": { "height": 1170041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5df878a09d33742ef0a7e430d0e9a91a0481280c73d6cc5b54c0858e8962a37e" } } ], "extra": [ 1, 138, 102, 71, 72, 196, 112, 50, 177, 70, 248, 73, 140, 152, 72, 97, 40, 197, 183, 180, 204, 62, 193, 40, 106, 28, 85, 82, 83, 206, 70, 238, 82, 2, 17, 0, 0, 0, 8, 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