Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7014f407702a6fdf9b30da493a55869306263a963690a72c2283b1b0060cdaa1

Tx prefix hash: fbf3dac40b5191969d64bb6bc9a37d0fe1f4a1f605456ced8560b3e8bb08ea98
Tx public key: 8d1f79d295ce221fce1c55113f7c06d7f475a96609338588e5713d961ae17f8d
Timestamp: 1764470817 Timestamp [UCT]: 2025-11-30 02:46:57 Age [y:d:h:m:s]: 00:005:01:39:27
Block: 1423113 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3638 RingCT/type: yes/0
Extra: 018d1f79d295ce221fce1c55113f7c06d7f475a96609338588e5713d961ae17f8d02110000000217b19132000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89c3a778ebe0a33b78fef5be9067cec12ae0d2dcb22e28a5088926cbf4985ed6 0.600000000000 1911716 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": 1423123, "vin": [ { "gen": { "height": 1423113 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89c3a778ebe0a33b78fef5be9067cec12ae0d2dcb22e28a5088926cbf4985ed6" } } ], "extra": [ 1, 141, 31, 121, 210, 149, 206, 34, 31, 206, 28, 85, 17, 63, 124, 6, 215, 244, 117, 169, 102, 9, 51, 133, 136, 229, 113, 61, 150, 26, 225, 127, 141, 2, 17, 0, 0, 0, 2, 23, 177, 145, 50, 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