Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c69070cdd1abc6febd1ec8aeaf441e1e248ea6ea576ff2cc2ed70ccbbadc9f93

Tx prefix hash: 908f70c96730c6f21012a6d9321599f9a34cd89eaa6e2cb1eb4ce7ab25295620
Tx public key: 642cb07d898f539641c43e2dfe26d90565424d22c3fd7b1a92567252b3725f8e
Timestamp: 1759464091 Timestamp [UCT]: 2025-10-03 04:01:31 Age [y:d:h:m:s]: 00:004:18:45:02
Block: 1381605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3422 RingCT/type: yes/0
Extra: 01642cb07d898f539641c43e2dfe26d90565424d22c3fd7b1a92567252b3725f8e02110000000197baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8515afd6661e102e176b5ce0eaab301a4d4a45b6f1162594b50c431d9677e80f 0.600000000000 1869724 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": 1381615, "vin": [ { "gen": { "height": 1381605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8515afd6661e102e176b5ce0eaab301a4d4a45b6f1162594b50c431d9677e80f" } } ], "extra": [ 1, 100, 44, 176, 125, 137, 143, 83, 150, 65, 196, 62, 45, 254, 38, 217, 5, 101, 66, 77, 34, 195, 253, 123, 26, 146, 86, 114, 82, 179, 114, 95, 142, 2, 17, 0, 0, 0, 1, 151, 186, 249, 34, 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