Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d07a7dc5b52e4ea0b03390c5e96d5e24a18ab81ce11377307647a2035076de6

Tx prefix hash: 371585e2e847bf43ba8d563ca58780b11fd878b0d2e51be26cfedb5f48c39d90
Tx public key: 50a7b4aabaaaf8a0f83e9554ee86292d396a3b6892cad7592221cfef3daf3d4f
Timestamp: 1749549538 Timestamp [UCT]: 2025-06-10 09:58:58 Age [y:d:h:m:s]: 00:156:22:53:28
Block: 1301981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109859 RingCT/type: yes/0
Extra: 0150a7b4aabaaaf8a0f83e9554ee86292d396a3b6892cad7592221cfef3daf3d4f021100000004bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8405a5dff3f68b9149fbcdfc786d41251ed649efabfa2cab3725ec44528b36d3 0.600000000000 1789548 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": 1301991, "vin": [ { "gen": { "height": 1301981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8405a5dff3f68b9149fbcdfc786d41251ed649efabfa2cab3725ec44528b36d3" } } ], "extra": [ 1, 80, 167, 180, 170, 186, 170, 248, 160, 248, 62, 149, 84, 238, 134, 41, 45, 57, 106, 59, 104, 146, 202, 215, 89, 34, 33, 207, 239, 61, 175, 61, 79, 2, 17, 0, 0, 0, 4, 191, 81, 178, 162, 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