Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c629357c154cd55b2b6b11574aa43ac2007f43a8bcf4fd2b8e42a2324c19a28

Tx prefix hash: 722f5cc164b63365849172fbc857d030bbc0ca7956e9a6eb16a330b0370ff95a
Tx public key: 48c49d9c7577c4527ac9576f35a5d24a129669b2d8462c0fef2641c4ab9d2deb
Timestamp: 1758957922 Timestamp [UCT]: 2025-09-27 07:25:22 Age [y:d:h:m:s]: 00:090:17:00:30
Block: 1377432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64939 RingCT/type: yes/0
Extra: 0148c49d9c7577c4527ac9576f35a5d24a129669b2d8462c0fef2641c4ab9d2deb0211000000036130ce73000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5fcc4e201dffd90c9402f174ef9a3e9c118fe3c63f621f334a8efcde73a0a2a 0.600000000000 1865525 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": 1377442, "vin": [ { "gen": { "height": 1377432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5fcc4e201dffd90c9402f174ef9a3e9c118fe3c63f621f334a8efcde73a0a2a" } } ], "extra": [ 1, 72, 196, 157, 156, 117, 119, 196, 82, 122, 201, 87, 111, 53, 165, 210, 74, 18, 150, 105, 178, 216, 70, 44, 15, 239, 38, 65, 196, 171, 157, 45, 235, 2, 17, 0, 0, 0, 3, 97, 48, 206, 115, 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