Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a384c8a619dd5fc86435273eeaa28a6ad3ec4d1c5777073bc3eab8fd2438373f

Tx prefix hash: 8dd228f7e3ca3357a2b96adfe08450c751dbf2570e8b1ce5ba1dd51bc1e77e84
Tx public key: fe70a76b630d6210fc17a2b64fb923b7510111839b3aa076c61d5c5cc670c106
Timestamp: 1757070404 Timestamp [UCT]: 2025-09-05 11:06:44 Age [y:d:h:m:s]: 00:109:05:15:11
Block: 1361865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78105 RingCT/type: yes/0
Extra: 01fe70a76b630d6210fc17a2b64fb923b7510111839b3aa076c61d5c5cc670c106021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4239659f3a1e0541fdd46d178f9de5071a3af9115750e7f191df551033f20e08 0.600000000000 1849888 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": 1361875, "vin": [ { "gen": { "height": 1361865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4239659f3a1e0541fdd46d178f9de5071a3af9115750e7f191df551033f20e08" } } ], "extra": [ 1, 254, 112, 167, 107, 99, 13, 98, 16, 252, 23, 162, 182, 79, 185, 35, 183, 81, 1, 17, 131, 155, 58, 160, 118, 198, 29, 92, 92, 198, 112, 193, 6, 2, 17, 0, 0, 0, 5, 178, 247, 132, 196, 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