Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc99de9ef9d83189def1c2515fcc6c06142bcdbd4d1e02427fecf8a78d1ae8a9

Tx prefix hash: 39b2f1028dba6b706fe6a4f389c928d5de486ad0c8788172052dda8ad670b396
Tx public key: 6a0163c6928ad94bf048d69d3e647d68f484c0dfd533c209c48830b2e382ffa3
Timestamp: 1751600129 Timestamp [UCT]: 2025-07-04 03:35:29 Age [y:d:h:m:s]: 00:128:21:09:22
Block: 1318358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90373 RingCT/type: yes/0
Extra: 016a0163c6928ad94bf048d69d3e647d68f484c0dfd533c209c48830b2e382ffa302110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36c0dea97ed393399310c3693790434c38c458d1b493eadca0ba2a8a6f1eab40 0.600000000000 1806037 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": 1318368, "vin": [ { "gen": { "height": 1318358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36c0dea97ed393399310c3693790434c38c458d1b493eadca0ba2a8a6f1eab40" } } ], "extra": [ 1, 106, 1, 99, 198, 146, 138, 217, 75, 240, 72, 214, 157, 62, 100, 125, 104, 244, 132, 192, 223, 213, 51, 194, 9, 196, 136, 48, 178, 227, 130, 255, 163, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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