Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09e8374f2939cff4655227578ac74eba6d43c24a2ae3b1747f897e9ac2cb6de6

Tx prefix hash: 6004bcb7f4a7379b33e6e12ac89e85cbbe0f3371319ef1e62229273fc1963ff2
Tx public key: 61ed33c74ffd5d25432e82dbfb21636242bf243c0c41112cb678a2d5f5aa4941
Timestamp: 1743386470 Timestamp [UCT]: 2025-03-31 02:01:10 Age [y:d:h:m:s]: 00:307:10:51:43
Block: 1250944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217391 RingCT/type: yes/0
Extra: 0161ed33c74ffd5d25432e82dbfb21636242bf243c0c41112cb678a2d5f5aa49410211000000091a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa66eac9b63e86791643363d8e35b499bd9efe053b61a3da2b7504fb8736c78d 0.600000000000 1738003 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": 1250954, "vin": [ { "gen": { "height": 1250944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa66eac9b63e86791643363d8e35b499bd9efe053b61a3da2b7504fb8736c78d" } } ], "extra": [ 1, 97, 237, 51, 199, 79, 253, 93, 37, 67, 46, 130, 219, 251, 33, 99, 98, 66, 191, 36, 60, 12, 65, 17, 44, 182, 120, 162, 213, 245, 170, 73, 65, 2, 17, 0, 0, 0, 9, 26, 151, 4, 3, 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