Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b24d190dd02c48ed44f7808bec0d7956ba320c2b97a0cf1d63ffb5fda4dc89e

Tx prefix hash: 676883375f2eb537bfe9b4cb0f609dd7c81a55d5073b9bf63238bb79b801803c
Tx public key: 1fb2e3e8a7bbacee0b13c0fa8617001cfb06659fec61c55440e0ed9f3996ede3
Timestamp: 1751363432 Timestamp [UCT]: 2025-07-01 09:50:32 Age [y:d:h:m:s]: 00:181:06:45:50
Block: 1316460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127833 RingCT/type: yes/0
Extra: 011fb2e3e8a7bbacee0b13c0fa8617001cfb06659fec61c55440e0ed9f3996ede3021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76bf348c562f14cafa6e7f38f4264d8e2a15eee8d1ea06899a38d66c1d6ea906 0.600000000000 1804121 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": 1316470, "vin": [ { "gen": { "height": 1316460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76bf348c562f14cafa6e7f38f4264d8e2a15eee8d1ea06899a38d66c1d6ea906" } } ], "extra": [ 1, 31, 178, 227, 232, 167, 187, 172, 238, 11, 19, 192, 250, 134, 23, 0, 28, 251, 6, 101, 159, 236, 97, 197, 84, 64, 224, 237, 159, 57, 150, 237, 227, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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